Skip to content

SEI-13992 Update Harness SEI Left-Hand Navigation Menu #11598

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

SEI-13992 Update Harness SEI Left-Hand Navigation Menu #11598

wants to merge 2 commits into from

Conversation

alai97
Copy link
Contributor

@alai97 alai97 commented Sep 17, 2025 •
edited
Loading

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

  • Successful preview build.
  • Code owner review.
  • No merge conflicts.
  • Release notes/new features docs: Feature/version released to at least one prod environment.

@bot-gitexp-user
Copy link

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68ca1ef8f30e017c1ba90ba8--harness-developer.netlify.app

@joeyouss
Copy link
Collaborator

@alai97 just one suggestion: Since we have "Use SEI 2.0" as heading already then we have "SEI 2.0" under it, I feel that is a bit repetitive -> maybe we can remove the SEI 2.0 heading and directly expose the folders in it under "Use SEI 2.0"?

@alai97
Copy link
Contributor Author

alai97 commented Sep 17, 2025

@alai97 just one suggestion: Since we have "Use SEI 2.0" as heading already then we have "SEI 2.0" under it, I feel that is a bit repetitive -> maybe we can remove the SEI 2.0 heading and directly expose the folders in it under "Use SEI 2.0"?

Hi @joeyouss, thanks for the suggestion! The wrinkle here is that users can toggle between SEI 1.0 and 2.0 in-app, so we've kept the headings consistent with the UI.

Screenshot 2025-09-17 at 11 19 55 AM Screenshot 2025-09-17 at 11 20 05 AM

I agree the repetition between SEI 2.0 (Recommended) and SEI 1.0 (Legacy) dropdowns is a little noticeable, but my thought was to keep it explicit: SEI 2.0 is the recommended path for new users, while SEI 1.0 remains available for existing users as they transition into SEI 2.0.

Curious if that framing makes sense to you, or if you see another way we could highlight “recommended vs. legacy” without losing clarity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@codewdhruv codewdhruv Awaiting requested review from codewdhruv codewdhruv is a code owner

@santoshdodamani santoshdodamani Awaiting requested review from santoshdodamani santoshdodamani is a code owner

@wei-harness wei-harness Awaiting requested review from wei-harness wei-harness is a code owner

@ivikramsahu ivikramsahu Awaiting requested review from ivikramsahu ivikramsahu is a code owner

@SushrutHarness SushrutHarness Awaiting requested review from SushrutHarness SushrutHarness is a code owner

@richardblack-Harness richardblack-Harness Awaiting requested review from richardblack-Harness richardblack-Harness is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@alai97 @bot-gitexp-user @joeyouss